Method for analyzing performance information

ABSTRACT

A performance information display method using a computer, includes the steps, in the computer, of reading out information data of a storage device previously stored in a storage device and information data of a plurality of devices utilizing the storage device, displaying an identifier of the storage device and identifiers of a plurality of devices utilizing the storage device on a screen on the basis of the information data read out, accepting a command to select the displayed identifier of the storage device, and displaying performance information data of the devices utilizing the selected storage device in association on the basis of the accepted command and the information data read out.

BACKGROUND OF THE INVENTION

The present invention relates to a system for displaying/analyzingperformance information of servers and storage devices.

In recent years, configurations in which a plurality of servers share asingle storage device have increased because of the development of theSAN (Storage Area Network) technique. The reason why such configurationsare increasing is that the localization of the operational business suchas backup and fault control is facilitated and the operation managementcost can be compressed.

On the other hand, however, since a plurality of servers share a singlestorage device, volume assignment and storage performance managementbecome complicated. A method for simplifying the volume assignment inthe SAN environment is disclosed in U.S. Ser. No. 2003/0005119A1.

In computer systems, the storage device is a low speed storage medium ascompared with caches and memories in the CPU. Often, therefore, thestorage device becomes a bottleneck for the whole system. Therefore, itis important to acquire various performance index values in theconstruction phase and the operation phase and make an analysis todetermine whether predetermined performance values have been obtained sothat the storage device may exhibit as high performance as possible.

In a configuration in which a plurality of servers share and use asingle storage device, I/O transactions from a plurality of serversoverlap on a specific resource within the storage device andconsequently serious performance degradation is caused in some cases.

As an example, I/O loads from a plurality of servers concentrate on aspecific physical disk group within a storage device, and the I/Operformance seen from the server side is not sufficiently exhibited dueto the I/O contention.

Owing to a tool provided by the storage device, the I/O quantityprocessed by a specific resource within the storage device can beperused/analyzed. In this method, however, it is difficult todiscriminate the cause of an I/O contention performance problem causedby setting on the outside of the storage device, i.e., specifically aserver group that burdens an I/O load on a specific resource within thestorage device or a portion that becomes a bottleneck of theperformance.

SUMMARY OF THE INVENTION

An object of the present invention is to provide a method for solvingthe above-described problem and facilitating the discrimination of aserver group that is causing I/O contention on a resource in a storagedevice and a portion that has become a bottleneck in performance.

In accordance with the present invention, a performance informationdisplay method using a computer includes the steps, in the computer, ofreading out information data of a storage device previously stored in astorage device and information data of a plurality of devices utilizingthe storage device, displaying an identifier of the storage device andidentifiers of a plurality of devices utilizing the storage device on ascreen on the basis of the information data read out, accepting acommand to select the displayed identifier of the storage device, anddisplaying performance information data of the devices utilizing theselected storage device in association on the basis of the acceptedcommand and the information data read out.

The present invention provides a method of taking a specific resourcewithin the storage device as a starting point and displaying at a strokeperformance index values of a server group that burdens the load on theresource. Specifically, a performance management tool according to thepresent invention collects mapping information between the storagedevice and the servers and performance information of the server group.If there is a command from the user, the performance management toolsearches the mapping information between the storage device and theservers for the server group utilizing a specific resource within thestorage device, and creates a report of I/O contention narrowed down tothe performance data of the server group.

Other objects, features and advantages of the invention will becomeapparent from the following description of the embodiments of theinvention taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing a configuration of a SAN system in anembodiment;

FIG. 2 is a diagram showing a volume provisioning function of a storagedevice and a volume mount function of a server;

FIG. 3 is a diagram showing an internal structure of a performanceinformation repository;

FIG. 4 is a diagram showing a cooperation method between a performanceinformation collection program and a performance information analysisprogram;

FIG. 5 is a diagram showing data items stored in a server performanceinformation table;

FIG. 6 is a diagram showing data items stored in a server storagemapping table;

FIG. 7 is a diagram showing data items stored in a storage RAID groupperformance information table;

FIG. 8 is a diagram showing data items stored in a storage portperformance information table;

FIG. 9 is a diagram showing SCSI inquiry response information;

FIG. 10 is a flow chart showing processing of a server performanceinformation collection program;

FIG. 11 is a flow chart showing processing of a storage performanceinformation collection program;

FIG. 12 is a diagram showing an internal structure of a performanceinformation analysis program and schematic views that are output by theperformance information analysis program;

FIG. 13 is a diagram showing an embodiment of a storage performanceinformation view;

FIG. 14 is a diagram showing an embodiment of a related serverperformance information view;

FIG. 15 is a diagram showing an embodiment of a related serverperformance history information view;

FIG. 16 is a flow chart showing processing of a storage performanceinformation display subprogram;

FIG. 17 is a flow chart showing processing of a related serverperformance information display subprogram; and

FIG. 18 is a flow chart showing processing of a related serverperformance history information display subprogram.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Hereafter, an embodiment of the present invention in a SAN system inwhich a plurality of servers share a storage device will be described.

Examples of the SAN system in the embodiment described hereafter aresimplified as compared with the ordinary SAN system because functionsand details that are not necessary for description of the presentembodiment are omitted. However, the application range of the presentembodiment is not limited thereby.

FIG. 1 is a diagram showing a configuration of a SAN system in thepresent embodiment. The present SAN system includes a storage device A120, a server group including a server A 110A and a server B 110B, a SAN140 for connecting the server group and the storage device to eachother, a management server 130, and a LAN 150 for connecting the servergroup and the storage device to the management server 130. Each of theservers may be a computer in which a program is executed, a terminaldevice using the function of the computer, or a different one.

Each of the server group and the storage device A transmits itsperformance information to the management server 130 via the LAN 150,and the management server 130 stores the performance information in itsinternal secondary storage device.

The server A 110A is connected to the SAN 140 via an HBA 114. The serverA 110A executes a volume mount function 111A for mounting a volumeprovided from the storage device A 120, a business program 112A forconducting business processing by using the mounted volume, and a serverperformance information collection program 101 for collectingperformance information of a server volume.

In the same way as the server A, the server B 110B is connected to theSAN 140 via an HBA, and the server B 110B executes a volume mountfunction, a business program, and a server performance informationcollection program. Here, the SAN and LAN are used as example of thenetworks. However, other networks such as NASs (Network AttachedStorages) may also be used.

The storage device A 120 is connected to the SAN 140 via a port A 123and a port B 124. Within the storage device A 120, a volume provisioningfunction 121 for providing a volume for the SAN side and a storageperformance information collection program 102 for collectingperformance information of the storage device are executed.

In the present embodiment, it is supposed for brevity that one storagedevice is used, and the server group using the volume provided by thestorage device A 120 includes only two servers: the server A 110A andthe server B 110B. However, the present embodiment can also be appliedto a configuration having more storage devices and more servers.

The management server 130 includes a secondary storage device 161, amain storage device 162, a communication device 163, a CPU 164, adisplay device 165, a keyboard 166 and a mouse 167. Although notillustrated, the management server 130 also includes functions such as afile system required for a server to recognize data stored in thestorage device.

A performance information repository 103 for preserving performanceinformation of the server group and the storage device A 120 is storedin the secondary storage device 161. An operating system 168 is storedin the main storage device 162. Within the operating system 168, aperformance information analysis program 104 for analyzing performanceinformation stored in the performance information repository 103 anddisplaying a result of the analysis on the display device 165.

FIG. 2 is a diagram showing the volume provisioning function in thestorage device A 120 and the volume mount function in the server group.

First, the volume provisioning function will now be described. Thevolume provisioning function 120 in the present embodiment provides afunction of enhancing the usability of physical disk groups in thestorage device A 120 by using a configuration of the RAID (RedundantArray of Independent Disks), slicing a RAID group, which is virtualdisks having a RAID configuration, in sizes that can be easily used byhigher rank servers, and making logical volumes obtained as a result ofthe slicing usable from the SAN side via a port. By thus combining aplurality of disks, it becomes possible to make the disk access fast andenhance the fault resistance against failures of disks.

Specifically, the storage device A 120 includes eight physical disks,i.e., a physical disk A 240A, a physical disk B 240B, a physical disk C240C a physical disk D 240D, a physical disk E 240E, a physical disk F240F, a physical disk G 240G and a physical disk H 240H. In the presentembodiment, the volume provisioning function 121 creates two RAIDgroups, i.e., a RAID group A 230A and a RAID group B 230B by using thesephysical disks.

The RAID group is the unit obtained by regarding a plurality of physicaldisk groups having a RAID configuration as one virtual disk.

Furthermore, in the present embodiment, the volume provisioning function121 logically slices the created RAID group, and creates six logicalvolumes as volumes that can be easily used by higher rank servers. Inother words, the volume provisioning function 121 creates a logicalvolume A 220A, a logical volume B 220B and a logical volume C 220C froma RAID group A 230A, and creates a logical volume D 220D, a logicalvolume E 220E and a logical volume F 220F from a RAID group B 230B.Furthermore, the volume provisioning function 121 opens the logicalvolumes to ports and makes the logical volumes accessible from the SAN140 side.

For example, if an I/O request is issued to the logical volume A by aserver via the port A, the I/O request is temporarily converted to anI/O request for a corresponding slice portion within the RAID group A,and in addition it is further converted to an I/O request extending overthe physical disk A 240A to the physical disk D 240D, which physicallyform the RAID group A, by the volume provisioning function 121, andprocessed.

The volume mount function will now be described. The volume mountfunction 111A in the server A 110A mounts volumes opened to the SAN 140side from the storage device A 120 into the server A 110A, and makes thevolumes usable from the business program 112A. The same holds true forthe server B 110B as well. Typically, such a volume mount function isprovided as a part of an operating system.

Finally, correlation between server side volumes and storage sidevolumes in the present embodiment will now be described. In the presentembodiment, the server A 110 a mounts the two volumes, i.e., the volumeA 210A and the volume B 210B from the storage device A 120 and usesthem. The volume A 210A and the volume B 210B correspond to the logicalvolume A 220A and the logical volume B 220B in the storage device A 120,respectively.

The server B 110B mounts a volume C 210C from the storage device A 120,and uses it. The volume C 210C corresponds to the logical volume C 220Cin the storage device A 120. All of the logical volumes A, B and C arelogical volumes sliced from the RAID group A 230A. In the presentembodiment, therefore, I/O loads of the server A and the server B becomeloads of the same RAID group A, and it can be said that physicalcontention might occur between I/Os in the situation.

FIG. 3 is a diagram showing an internal structure of the performanceinformation repository 103 stored in the secondary storage device 161 inthe management server 130. The performance information repository 103includes four tables. A server performance information table 310 is atable storing performance information for the volumes in the servergroup. A server storage mapping table 320 is a table storing mappinginformation among the volumes in the servers, the ports in the storagedevice, the logical volumes and the RAID groups. A storage RAID groupperformance information table 330 is a table storing performanceinformation for RAID groups in the storage device. A storage portperformance information table 340 is a table storing performanceinformation for ports in the storage device.

FIG. 4 is a diagram showing a cooperation method between the performanceinformation collection program 101 and the performance informationanalysis program 104.

As described earlier, the server performance information collectionprogram 101 is operating on the server A 110A and the server B 110B. Theserver performance information collection program 101 collectsperformance information for the volumes on the server, and adds recordsto the server performance information table 310 and the server storagemapping table 320 on the performance information repository 103.

The storage performance information collection program 102 is operatingin the storage device A 120. The storage performance informationcollection program 102 collects performance information for the portsand the RAID groups in the storage device, and adds records to thestorage RAID group performance information table 330 and the storageport performance information table 340 on the performance informationrepository 103.

The performance information analysis program 104 is operating on themanagement server 130. In response to a request from the user, theperformance information analysis program 104 acquires and analyzes theperformance information data on the performance information repository103, and displays its result on the display device 165.

FIG. 5 is a diagram showing data items stored in the server performanceinformation table 310 in detail. The present table is a table storingI/O performance information for the volumes on the servers, and it is atable to which records are added by the server performance informationcollection program 101. In the present embodiment, the present tableincludes a server column 511 and a volume column 512, serving as columnsfor uniquely identifying servers and volumes.

The present table includes an IOPS (IO per second) column 513, a ReadIOPS (IO per second) column 514 and a Write IOPS (IO per second) column515 respectively representing the number of IO times, the number of readIO times and the number of write IO times per second for respectivevolumes.

The present table includes an Xfer (Transfer) column 516, a Read Xfer(Transfer) column 517 and a Write Xfer (Transfer) column 518respectively representing the transfer data quantity, read transfer dataquantity and the write data quantity per second for respective volumes.Finally, the present table 310 includes a TS column 519 representingtime when the performance information was observed.

FIG. 6 is a diagram showing data items stored in the server storagemapping table 320 in detail. The present table is a table representingeach volume in each server corresponds to which logical volume and whichRAID group via which port in the storage device, and it is a table towhich records are added by the server performance information collectionprogram 101.

In the present embodiment, the present table includes a server column611 and a volume column 612, serving as columns for uniquely identifyingservers and volumes. The present table includes a storage column 613, aport column 614, a logical volume column 615, and a RAID group column616, which represent each volume is using which one of storage devices,ports, and logical volumes and RAID groups.

In the present embodiment, it is supposed that the server storagemapping table 320 has only the latest mapping information. However, itis also possible to add a mapping information acquisition time column tothe present table to provide the present table with past historyinformation of the mapping information, and thereby create a reporthaving related server groups narrowed down on the basis of the pastmapping information.

FIG. 7 is a diagram showing data items stored in the storage RAID groupperformance information table 330 in detail. The present table is atable storing I/O performance information for respective RAID groups inrespective storage devices, and it is a table to which records are addedby the storage performance information collection program 102. In thepresent embodiment, the present table includes a storage column 711 andan RAID group column 712, serving as columns for uniquely identifyingRAID groups on storage devices. The present table includes an IOPS (IOper second) column 713, a Read IOPS (IO per second) column 714 and aWrite IOPS (IO per second) column 715 respectively representing thenumber of IO times, the number of read IO times and the number of writeIO times per second for respective RAID groups.

The present table includes an Xfer (Transfer) column 716, a Read Xfer(Transfer) column 717 and a Write Xfer (Transfer) column 718respectively representing the transfer data quantity, the read transferdata quantity and the write data quantity per second for respective RAIDgroups. Finally, the present table includes a TS column 719 representingtime when the performance information was observed.

FIG. 8 is a diagram showing data items stored in the storage portperformance information table 340 in detail. The present table is atable storing I/O performance information for respective ports inrespective storage devices, and it is a table to which records are addedby the storage performance information collection program 102.

In the present embodiment, the present table includes a storage column811 and a port column 812, serving as columns for uniquely identifyingports on storage devices. The present table includes an IOPS (IO persecond) column 813, a Max IOPS (IO per second) column 814 and a Min IOPS(IO per second) column 815 respectively representing the number of IOtimes, the maximum number of IO times and the minimum number of IO timesper second for respective ports. The present table includes an Xfer(Transfer) column 816, a Read Xfer (Transfer) column 817 and a WriteXfer (Transfer) column 818 respectively representing the transfer dataquantity, the maximum transfer data quantity and the minimum dataquantity per second for respective ports. Finally, the present tableincludes a TS column 819 representing time when the performanceinformation was observed.

FIG. 9 is a diagram showing SCSI inquiry response information. SCSIinquiries can be issued from the server to respective volumes. Theissued SCSI inquiry is transferred to a storage device via the SAN. Thestorage device returns SCSI inquiry response information shown in FIG. 9to the server side as its response.

In the present embodiment, the server performance information collectionprogram 101 issues SCSI inquiries to volumes on respective servers, andacquires information of a storage device side of connection destinationby utilizing returned SCSI inquiry response information. Furthermore, inthe present embodiment, the SCSI inquiry response information holds astorage device name, a port name, a logical volume name and a RAID groupname of the connection destination in a connection destination storagecolumn 911, a connection destination port column 912, a connectiondestination logical volume column 913 and a connection destination RAIDgroup column 914.

Here, an example in which various kinds of information are collected byusing an SCSI command is shown as an example. However, information maybe collected by using a method other than this.

FIG. 10 is a flow chart showing processing of the server performanceinformation collection program 101. The server performance informationcollection program 101 is a program for acquiring performanceinformation and storage device information of connection destination forall volumes on a server on which the present program operates and addingrecords to the performance information repository 103.

At step 1001, initialization processing for repetitively conductingprocessing for all volumes in the server is conducted.

At step 1002, the OS is requested to acquire the performance informationof the volume and its result is acquired. In the present embodiment, thenumber of IO times, the number of read IO times and the number of writeIO times per second, the transfer data quantity, the read transfer dataquantity and the write data quantity per second are acquired forrespective volumes, as an example.

At step 1003, the performance information of the volume acquired at thestep 1002 is added to the server performance information table 310together with a time stamp.

At step 1004, a SCSI inquiry is issued for the volume and SCSI inquiryinformation 910 is acquired. Furthermore, information of the storagedevice, port, logical volume and RAID group that are being utilized bythe volume is extracted from the acquired SCSI inquiry information 910.

At step 1005, connection destination information of the volume acquiredat the step 1004 is assed to the server storage mapping table 320. Ifmapping information of the volume already exists, it is deleted and thenaddition is conducted.

At step 1006, it is checked whether the volume is the last volume on theserver. If the volume is the last volume, the processing is finished. Ifthere are still remaining volumes, the processing returns to the step1002.

FIG. 11 is a flow chart showing processing of the storage performanceinformation collection program 101. The storage performance informationcollection program 101 is a program for acquiring performanceinformation for all ports and RAID groups on the storage device on whichthe present program operates, and adding records to the performanceinformation repository 103.

At step 1101, initialization processing for repetitively conductingprocessing for all ports in the storage device is conducted.

At step 1102, the storage device is requested to acquire the performanceinformation of the port and its result is acquired. In the presentembodiment, the number of IO times, the maximum number of IO times andthe minimum number of IO times per second, the transfer data quantity,the maximum transfer data quantity and the minimum data quantity persecond are acquired for respective ports, as an example.

At step 1103, the performance information of the port acquired at thestep 1102 is added to the storage port performance information table 340together with a time stamp.

At step 1104, it is checked whether the port is the last port on thestorage device. If the port is the last port, the processing proceeds tostep 1105. If there is a remaining port, the processing returns to thestep 1102.

At step 1105, initialization processing for repetitively conductingprocessing for all RAID groups in the storage device is conducted.

At step 1106, the storage device is requested to acquire the performanceinformation of the RAID group and its result is acquired. In the presentembodiment, the number of IO times; the number of read IO times and thenumber of write IO times per second, the transfer data quantity, theread transfer data quantity and the write data quantity per second areacquired for respective RAID groups, as an example.

At step 1107, the performance information of the RAID group acquired atthe step 1106 is added to the storage RAID group performance informationtable 330 together with a time stamp.

At step 1108, it is checked whether the RAID group is the last RAIDgroup on the storage device. If the RAID group is the last RAID group,the processing is finished. If there is a remaining RAID group, theprocessing returns to the step 1106.

FIG. 12 is a diagram showing an internal structure of the performanceinformation analysis program 104 and schematically showing a view thatis output by the present program.

The performance information analysis program 104 includes three internalsubprograms, i.e., a storage performance information display subprogram1201, a related server performance information display subprogram 1202and a related server performance history information display subprogram1203.

The storage performance information display subprogram 1201 is a programfor providing the user with performance information of ports and RAIDgroups in the storage device by displaying a storage performanceinformation view 1210.

The related server performance information display subprogram 1202 is aprogram for narrowing down volumes to volumes on the server sideutilizing ports or RAID group resources of a certain specific storageside and displaying performance information of a plurality of serverside volumes by displaying a related server performance information view1220.

The related server performance information view 1220 is started from thestorage performance information view 1210 according to a user's request.By watching the related server performance information view 1220, itbecomes easy for the user to discriminate a server that burdens a loadon a specific resource in the storage device. And by perusing theperformance information of the server group at a stroke, a server thatespecially burdens load on the resource can be discriminated.

The related server performance history information display subprogram1203 is a program for displaying performance history information of aserver group using a specific resource in the storage device in a timeseries form in the order of time when performance information wasobserved by displaying a related server performance history informationview 1230. The related server performance history information view 1230is started from the related server performance information view 1220according to a user's request.

FIG. 13 is a diagram showing an embodiment of the storage performanceinformation view 1210. The present view includes a storage objectselection region 1310, a performance display date and hour input region1320, a selected object performance information display region 1330 anda related server performance display button 1340.

In the present embodiment, a storage device and resources within thestorage device are displayed in a tree form in the storage performanceinformation view 1210. Specifically, in FIG. 13, a storage device A node1311 is displayed as a parent node of the tree, and RAID groups andports are displayed as child nodes like a RAID group A node 1312, a RAIDgroup B node 1313, a port A node 1314 and a port B node 1315. The usercan select one of the child nodes in the present storage objectselection region, and performance information concerning the selectedobject is displayed in the selected object performance informationdisplay region 1330.

In the present embodiment, kinds of resources within the storage to besubjected to the performance analysis are two kinds, i.e., the RAIDgroup and port. However, the present embodiment can also be applied toother resources such as cache memories in the storage device, and theapplication is not limited.

The performance display date and hour input region 1320 is a region forthe user to input the time when the performance information to bedisplayed. Performance information at the date and hour that has beeninput to the region is retrieved and displayed in the selected objectperformance information display region 1330. As for the specification ofthe date and hour for displaying the performance information, theprogram may previously specify that the current time should bedisplayed, or performance information in a predetermined interval may bedisplayed in time series order according to data accepted by the user.Other specification is also possible.

The selected object performance information display region 1330 is aregion for displaying performance information concerning an objectselected in the storage object selection region 1310 as regards the dateand hour that has been input in the performance display date and hourinput region 1320.

In FIG. 13, it is supposed that the RAID group A node 1312 has beenselected in the storage object selection region 1310 and “10 a.m., Jul.19, 2003” has been input as the performance display date and hour.Therefore, performance information of the RAID group A at 10 a.m., Jul.19, 2003 is displayed in the selected object performance informationdisplay region 1330. Specifically, the selected resource name, i.e.,“RAID group A” is displayed in a selected object display region 1337,and the performance information of the RAID group A at 10 a.m., Jul. 19,2003 is displayed in an IOPS (IO per second) column 1331, a Read IOPS(IO per second) column 1332, a Write IOPS (IO per second) column 1333,an Xfer (Transfer) column 1334, a Read Xfer (Transfer) column 1335 and aWrite Xfer (Transfer) column 1336.

The related server performance display button 1340 is a button forrequesting the display of the related server performance informationview 1220. By pressing the present button, it is possible to display therelated server performance information view 1220 for displaying theperformance information of a volume on the server side utilizing anobject selected in the storage object selection region 1310. On theinside, the present button starts the related server performanceinformation display subprogram 1202.

FIG. 14 is a diagram showing an embodiment of the related serverperformance information view 1220. The present view is a view thatdisplays a list of servers and volumes utilizing a specific RAID groupor port, and their performance information. By watching the presentview, the user can discriminate a server and a volume that burden theload on a specific RAID group or port.

The related server performance information view 1220 includes a relatedserver performance information display region 1410 and a historyinformation display button 1420.

The related server performance information display region 1410 is aregion for displaying a list of related servers and volumes and theirperformance information. In the present embodiment, the related serverperformance information display region 1410 includes a server column1421 and a volume column 1422 for specifying a server and a volume thatutilize the RAID group or port. Furthermore, in the present embodiment,an IOPS (IO per second) column 1423, a Write IOPS (IO per second) column1424, a Read IOPS (IO per second) column 1425, an Xfer (Transfer) column1426, a Read Xfer (Transfer) column 1427 and a Write Xfer (Transfer)column 1428 are displayed as the performance information of the volumein the related server performance information display region 1410.

The history information display button 1420 is a button for requestingthe display of the related server performance history information view1230. By pressing the present button, the related server performancehistory information view 1230 for historically displaying theperformance information of the related server group can be displayed. Onthe inside, the present button starts the related server performancehistory information display subprogram 1203.

FIG. 15 is a diagram showing an embodiment of the related serverperformance history information view 1230. The present view historicallydisplays the performance information of the related server group. Thepresent view includes a related server performance history informationdisplay region 1510. Historical performance information of the relatedserver is displayed in the related server performance historyinformation display region 1510 by broken line graphs as shown in FIG.15.

In FIG. 15, the abscissa of the graph indicates time, and the ordinateof the graph indicates performance, as an example. Performance historydata for the volume A in the server A and performance history data forthe volume C in the server B are displayed by superposition of brokenline graphs, and a server name and a volume name are added to each ofthe broken line graphs. However, this is an example, and performanceinformation of devices other than servers may also be displayed.

For example, performance information may be displayed by using one viewevery logical volume. In the case where volumes recognized by respectiveservers utilize the same RAID group, the performance information may bedisplayed by using a window every RAID group. Or other display methodsmay also be used.

It is also possible to partition one window into a plurality of partsand display various devices in a tree structure on a left-hand part ofthe window as represented by 1310 in FIG. 13. When the user has selectedone of components in the tree structure shown in 1310, performancehistory information display of related devices (for example, FIG. 15)may be conducted on a right-hand part of the window on the basis of theuser's selection.

Information data of devices sharing a storage device specified by theuser may be superposed and displayed by using graphs having the samecoordinate axes. The performance information of the specified storagedevice and performance information data of three devices having thehighest loads among devices utilizing the specified storage device maybe displayed so as to be associated with each other. A different displaymethod may also be used. When displaying a plurality of performanceinformation data, the performance information data may be displayed inone window so as to be superposed in the order of increasing value, theperformance information data may be displayed in one window inaccordance with a predetermined order, or a plurality of windows may bedisplayed side by side in the horizontal direction or the verticaldirection in association.

Thus, performance data of the devices and computers are not shownsingly, but they are displayed in association with performanceinformation of related devices on a path between a server and a storagedevice and performance information of devices sharing the storagedevice. As a result, it becomes easy to discriminate a part that becomesa performance bottleneck even in a complicated system environment.

It becomes possible to narrow down and display performance informationdata of related devices from among a large number of performanceinformation data. It becomes easy for a human being to understand theperformance information.

FIG. 16 is a flow chart showing processing of the storage performanceinformation display subprogram 1201. The present program is a programfor displaying the storage performance information view 1210.

The present program is broadly divided into two kinds of processing.Steps 1601 to 1603 are processing for drawing the storage objectselection region 1310. Processing ranging from the step 1604 to endprocessing is processing for drawing the selected object performanceinformation display region 1330.

At step 1601, the storage RAID group performance information table 330is scanned, and a list of pairs of all RAID groups and storage devicesto which the RAID groups belong is acquired.

At step 1602, the storage port performance information table 340 isscanned, and a list of pairs of all ports and storage devices to whichthe ports belong is acquired.

At step 1603, all storage devices, RAID groups and ports are drawn inthe storage object selection region 1310 on the basis of the list ofRAID groups paired with storage devices and the list of ports pairedwith storage devices acquired respectively at the steps 1601 and 1602.

At step 1604, date and hour information that has been input in theperformance display date and hour input region 1320 is acquired.

At step 1605, a name of an object selected in the storage objectselection region 1310 is acquired. For example, specification of anidentifier of an RAID group, a port name, and a name and an identifierof a storage related device is accepted.

At step 1607, on the basis of the name of the storage object acquired atthe step 1605, it is determined whether the object is an RAID group or aport. If the object is a RAID group, the processing proceeds to a step1608. If the object is a port, the processing proceeds to step 1610.

At step 1608, the storage RAID group performance information table 330is searched by using the object name acquired at the step 1605 and thedate and hour acquired at the step 1604 as a key, and performanceinformation of the selected RAID group at the specified date and hour isacquired.

At step 1609, performance information of the RAID group acquired at thestep 1608 is drawn in the selected object performance informationdisplay region 1330.

At step 1610, the storage port performance information table 340 issearched by using the object name acquired at the step 1605 and the dateand hour acquired at the step 1604 as a key, and performance informationof the selected port at the specified date and hour is acquired.

At step 1611, performance information of the port acquired at the step1610 is drawn in the selected object performance information displayregion 1330.

FIG. 17 is a flow chart showing processing of the related serverperformance information display subprogram 1202. The present program isa program that is executed to draw the related server performanceinformation view 1220 when the user has pressed the related serverperformance display button 1340 on the storage performance informationview 1210.

At step 1701, date and hour information that has been input in theperformance display date and hour input region 1320 is acquired.

At step 1702, a name of an object selected in the storage objectselection region 1310 is acquired.

At step 1703, on the basis of the name of the storage object acquired atthe step 1702, it is determined whether the object is an RAID group or aport. If the object is a RAID group, the processing proceeds to a step1704. If the object is a port, the processing proceeds to step 1705.

At step 1704, the server storage mapping table 320 is searched by usingthe object name acquired at the step 1702 as a key for the RAID groupcolumn, and a list of volumes of servers utilizing the RAID group isacquired.

At step 1705, the server storage mapping table 320 is searched by usingthe object name acquired at the step 1702 as a key for the port column,and a list of volumes of servers utilizing the port is acquired.

At step 1706, the server performance information table 310 is searchedby using the date and hour acquired at the step 1701 and the volume listof servers acquired at the step 1704 or 1705 as a key, and performanceinformation of the volume group of the server side utilizing the RAIDgroup or the port is acquired.

At step 1707, performance information of the related server acquired atthe step 1706 is drawn in the related server performance informationdisplay region 1410.

FIG. 18 is a flow chart showing processing of the related serverperformance history information display subprogram 1203. The presentprogram is a program that is executed to draw the related serverperformance history information view 1230 when the user has pressed thehistory information display button 1420 on the related serverperformance information view 1220.

At step 1801, a list of volumes of the server side displayed in therelated server performance information region 1410 is acquired.

At step 1802, the server performance information table 310 is searchedby using the volume list of the server side acquired at the step 1801 asa key, and historical performance data of the volume group is acquired.

At step 1803, the related server performance history information view1230 is created, and historical performance data of related volumesacquired at the step 1802 are drawn in the related server performancehistory information display region 1510.

The above-described processing and display transition are an example,and different view transition may be conducted. For example, in the casewhere the user has specified the RAID group A node 1312 in the viewshown in FIG. 13 with a mouse pointer or the like, load information of aplurality of servers utilizing the RAID group A may be displayed in aform of superposed graphs (for example, as shown in FIG. 15).Furthermore, a port may be specified and load information of a serverutilizing the port may be displayed on the basis of the specified portinformation. Or it is also possible to associate route informationutilizing the port with a storage device on the route (for example, in aform such as “server-volume name-switch (I/O port)-logical volume-RAIDgroup-physical disk”), and display information relating to each of thestorage devices. Different display may also be conducted.

Furthermore, in the case where the fact that the I/O performance of acertain server has degraded is detected, it is also possible to regardthe server degraded in performance as a reference point and displayperformance information of ports utilized by the server and informationof servers utilizing the ports. Or it is also possible to check logicalvolumes and RAID groups utilized by the server, and display performanceinformation of other servers sharing and utilizing the logical volumesand RAID groups.

As described above, according to the storage resource contentionsituation detection method, a specific resource within the storagedevice is regarded as the starting point, and performance index valuesof the server group (or various devices) that burdens the load on theresource are displayed at a stroke. In a configuration in which aplurality of servers share and utilize a single storage device,therefore, it is possible to easily detect concentration of I/O loads ona resource within the storage device and easily discriminate serversthat burden the load.

Furthermore, in the case where a plurality of storage devices or aplurality of servers share various devices, it becomes easy to grasp thestate of a device that becomes a bottleneck in performance of the shareddevices by collecting and analyzing performance information of relateddevices.

According to the present invention, performance values of devices thatburden the load on a storage device are displayed in association. As aresult, it is possible to easily discriminate a server group that causesI/O contention on a resource in the storage device, or a part thatbecomes a bottleneck in performance.

It should be further understood by those skilled in the art thatalthough the foregoing description has been made on embodiments of theinvention, the invention is not limited thereto and various changes andmodifications may be made without departing from the spirit of theinvention and the scope of the appended claims.

1. A performance information display method using a computer, comprisingthe steps, in the computer, of: reading out information data of astorage device previously stored in the storage device and informationdata of a plurality of computers utilizing the storage device, bothinformation data previously stored in a memory device of the computer;displaying a RAID group identifier of the storage device on a screen onthe basis of the read out information data of the storage device;accepting a command to select the displayed RAID group identifier of thestorage device; and displaying performance information data of part ofthe plurality of computers utilizing a RAID group indicated by theselected RAID group identifier on the basis of the accepted command andthe both information data read out, the performance information of thepart of the plurality of computers corresponding to the RAID group ofthe storage device.
 2. A performance information analysis method in asystem including a storage device and a plurality of servers, theperformance information analysis method comprising: a server volumeperformance information collection step of collecting performanceinformation data for respective volumes on respective servers; a serverstorage mapping information collection step of collecting identifiers ofresources in the storage device utilized by the respective volumes onthe respective servers; and a narrowed down server volume performanceinformation output step of narrowing down only server volumes utilizinga specific resource in a specific storage device from the collectedperformance information data by using the specific resource as a key,and outputting performance information data of the server volumesnarrowed down.
 3. The performance information analysis method accordingto claim 2, wherein said server storage mapping information collectionstep comprises a substep of acquiring mapping information by issuing aSCSI inquiry to volumes on the servers.
 4. The performance informationanalysis method according to claim 2, wherein said server volumeperformance information collection step comprises a substep of storingperformance information data in time series order, and said narroweddown server volume performance information output step comprises asubstep of outputting performance information data of narrowed downservers in time series order.
 5. A method for executing collection andanalysis of performance information by using mechanical processing in asystem in which a plurality of servers share a storage device, themethod comprising: a storage performance information collection step ofcollecting performance information data of resources in the storagedevice; a server volume performance information collection step ofcollecting performance information data for respective volumes onrespective servers; a server storage mapping information collection stepof collecting identifiers of resources in the storage device utilized byrespective volumes on respective servers; a storage resource selectionstep of displaying resources within the storage device and theirperformance information data, and making a user arbitrarily select aresource included in the storage device; and a narrowed down servervolume performance information output step of narrowing down only servervolumes utilizing a specific resource within the storage device from thecollected performance information data by using the specific resource asa key, and outputting performance information data of the server volumesnarrowed down.
 6. The method for executing collection and analysis ofperformance information by using mechanical processing according toclaim 5, wherein said server storage mapping information collection stepcomprises a substep of acquiring mapping information by issuing a SCSIinquiry to volumes on the servers.
 7. The method for executingcollection and analysis of performance information by using mechanicalprocessing according to claim 5, wherein said server volume performanceinformation collection step comprises a substep of storing performanceinformation data in time series order, and said narrowed down servervolume performance information output step comprises a substep ofoutputting performance information data of narrowed down servers in timeseries order.
 8. A performance information analysis method in a systemincluding a storage device and a plurality of servers coupled to thestorage device, the performance information analysis method comprising:an intra-server volume performance information collection step ofcollecting performance information data for volumes, mounted on servers,corresponding to RAID groups in the storage device; a server storagemapping information collection step of collecting identifiers of RAIDgroups in the storage device utilized by the volumes on the servers; anda narrowed down volume performance information output step of narrowingdown the volumes to part of the volumes utilizing a specific RAID groupof the RAID groups in the storage device by using the specific RAIDgroup as a key, and outputting performance information data of the partof the volumes narrowed down.